Constraint data statistics

ABSTRACT

Disclosed herein are system, method, and computer program product embodiments for using a data statistic as a dynamic data integrity constraint. An embodiment operates by defining a data statistic for a column or a set of columns of a partition of a plurality of partitions of a database table. The embodiment creates a constraint data statistics object based on the data statistic. The embodiment receives a query for the database table. The embodiment determines the constraint data statistics object is consistent with a data state of the partition. The embodiment derives an implied constraint based on the constraint data statistics object. The embodiment processes the query for the partition based on the implied constraint.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.15/796,326, filed Oct. 27, 2017, now allowed, which claims the benefitof provisional U.S. Patent Application No. 62/505,485, titled “DataStatistics As Data Integrity Constraints In A Database ManagementSystem” filed on May 12, 2017, all of which are incorporated herein byreference in their entirety.

BACKGROUND Background

A database management system (DBMS) often applies data integrityconstraints during query processing to improve query processing time andreduce memory consumption. For example, a DBMS may use partitionconstraints to perform partition pruning during query processing.

In partition pruning, a database administrator may define partitionconstraints for a database table using Data Definition Language (DDL)commands. The DBMS may use the partition constraints to createphysically independent partitions for the database table. This mayenable the DBMS to avoid scanning, and loading into main memory, one ormore irrelevant partitions of the database table in response to a query.Partition pruning may improve query processing time and reduce memoryconsumption.

For example, a database administrator may partition an ORDERS databasetable containing a historical record of orders by year. The DBMS maythen process a query for orders made in a particular time period byskipping partitions irrelevant to the query.

A DBMS may further improve query processing time and reduce memoryconsumption by applying a dynamic data integrity constraint during queryprocessing. A dynamic integrity constraint may describe a snapshot ofthe database state such as data location and system topology.

For example, a DBMS may apply a dynamic data integrity constraint thatpartitions a database table into a hot partition containing recentlyaccessed data and one or more cold partitions containing data that hasnot been recently accessed. The DBMS may store the hot partition in afast, low latency storage such random access memory (RAM). This isbecause the DBMS expects the hot partition to be more frequentlyaccessed than the one or more cold partitions. The DBMS may store theone or more cold partitions in a slower, higher latency storage devicesuch as hard disk drive. This partitioning scheme may enable the DBMS toscan and process a smaller amount of data.

For example, in response to a query for a recently accessed data record,the DBMS may scan and process the data record in the hot partition fromthe fast, low latency storage and skip the one or more cold partitionsthat are irrelevant to the query. This dynamic partition pruning processmay improve query processing time and reduce memory consumption becausethe DBMS does not need to scan, or load into main memory, the one ormore cold partitions.

But a DBMS often does not utilize dynamic data integrity constraints toimprove query processing time and reduce memory consumption. This isbecause dynamic data integrity constraints are often expensive todiscover and maintain for a DBMS.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are incorporated herein and form a part of thespecification.

FIG. 1 is a block diagram of a database system that uses traditionaldata statistics as dynamic data integrity constraints, according to someembodiments.

FIG. 2 illustrates a database table with dynamic partition pruning usingconstraint data statistics objects, according to some embodiments.

FIG. 3 is a block diagram of a constraint data statistics object,according to some embodiments.

FIG. 4 is a flowchart illustrating a process for using traditional datastatistics objects as dynamic data integrity constraints, according tosome embodiments.

FIG. 5 is a flowchart illustrating a process for dynamic partitionpruning using data statistics objects as data integrity constraints,according to some embodiments.

FIG. 6 is a flowchart illustrating a process for performing consistencychecking of constraint data statistics objects, according to someembodiments.

FIG. 7 is an example computer system useful for implementing variousembodiments.

In the drawings, like reference numbers generally indicate identical orsimilar elements. Additionally, generally, the left-most digit(s) of areference number identifies the drawing in which the reference numberfirst appears.

DETAILED DESCRIPTION

Provided herein are system, apparatus, device, method and/or computerprogram product embodiments, and/or combinations and sub-combinationsthereof, for using traditional data statistics as dynamic data integrityconstraints. Provided herein are system, apparatus, device, methodand/or computer program product embodiments, and/or combinations andsub-combinations thereof, for determining that a traditional datastatistic is consistent with a data state of a database. Provided hereinare system, apparatus, device, method and/or computer program productembodiments, and/or combinations and sub-combinations thereof, forperforming dynamic partition pruning using traditional data statistics.

FIG. 1 illustrates a database system 100 that uses traditional datastatistics as dynamic data integrity constraints, according to anexample embodiment. For example, FIG. 1 illustrates using constraintdata statistics objects as dynamic data integrity constraints. FIG. 1further illustrates performing dynamic partition pruning usingconstraint data statistics objects. As would be appreciated by a personof ordinary skill in the art, database system 100 may also useconstraint data statistics objects as dynamic data integrity constraintsto perform query optimization, semi-join reduction optimization, querytransformation, or other various other types of operations.

In some embodiments, database system 100 includes a database managementsystem 102 and a database 104. Database management system 102 may be acollection of computer software programs that control the organization,storage, and retrieval of data in database 104. A request to query,insert, or update data in database 104 may be performed as a databasetransaction by database management system 102.

In some embodiments, database 104 may be a relational database. Arelational database may organize data as a set of database tables fromwhich data can be accessed or reassembled in different ways withouthaving to reorganize the database tables.

For example, in some embodiments, database 104 includes database table106. Database table 106 may contain one or more data categories incolumns. Each row may contain a unique instance of data for thecategories defined by the columns. For example, a business order entrydatabase may include a table that describes a customer with columns forname, address, phone number, and so forth. Each row may have a primarykey. A primary key may be a column, or combination of columns,designated to uniquely identify a row.

In some embodiments, database table 106 may be represented using eitherrow-based storage or column-based storage. In row-based storage,database management system 102 may store data in database table 106 rowby row. In column-based storage, database management system 102 maystore data in database table 106 column by column.

In some embodiments, database management system 102 may apply a dynamicdata integrity constraint during query processing to improve queryprocessing time and reduce memory consumption. A dynamic data integrityconstraint may describe a snapshot of a data state of database 104 suchas data location and system topology. For example, database managementsystem 102 may use a dynamic data integrity constraint to restrictaccess to infrequently used data (e.g., cold data) that is not relevantto a query. But a dynamic data integrity constraint is often expensiveto discover and maintain for database management system 102. This mayreduce the usage of a dynamic data integrity constraint by databasemanagement system 102.

In some embodiments, database management system 102 may also improveperformance using traditional data statistics. But traditional datastatistics can also be expensive to create and maintain when datachanges.

However, in some embodiments, database management system 102 mayefficiently create and maintain traditional data statistics using datastatistics objects. A data statistics object may track a data statisticin database 104. For example, many commercial database managementsystems (e.g., SAP HANA) may have support for data statistics objects.

In some embodiments, database management system 102 may build andmaintain data statistics objects. For example, database managementsystem 102 may update the data statistics objects when data changes.Database management system 102 may also provide an applicationprogramming interface (API) for answering statistical questions of thedata statistic objects.

In some embodiments, building and maintaining data statistics objects issimilar to discovering and maintaining dynamic data integrityconstraints. Moreover, in some embodiments, a data statistics object mayhave an implied dynamic data integrity constraint associated with it.For example, database management system 102 may extract data as a twobucket histogram from a column A of database table 106 as [10, 100,payload1] and [200, 300, payload2]. This may imply a dynamic dataintegrity constraint of (column A of database table 106 between 10 and100) or (column A of database table 106 between 200 and 300). Moreover,in some embodiments, the data statistics object may imply a new dynamicdata integrity constraint when database management system 102 rebuildsthe data statistics object.

In some embodiments, database management system 102 may use a datastatistics object as a dynamic data integrity constraint based on theobservation that the data statistics object may imply a dynamic dataintegrity constraint. In some embodiments, this type of data statisticsobject may be referred to as a constraint data statistics object.

In some embodiments, a constraint data statistics object is a specialtype of data statistics object. A database administrator may define aconstraint data statistics object. A constraint data statistics objectmay leverage a traditional data statistic as an implied dynamic dataintegrity constraint.

In some embodiments, the implied dynamic data integrity constraint maybe defined for a column of a partition of database table 106. Forexample, the constraint data statistics object may have an implieddynamic data integrity constraint that is defined as a (minimum,maximum) value pair for a column of a partition of database table 106.The minimum value of the pair may represent the smallest value in thecolumn of the partition of database table 106. The maximum value of thepair may represent the largest value in the column of the partition ofdatabase table 106. As would be appreciated, the implied dynamic dataintegrity constraint may be defined in various other ways for databasetable 106 (e.g., for a column of database table 106).

In some embodiments, database management system 102 may use a constraintdata statistics object to improve query processing time and reducememory consumption by applying its associated implied dynamic dataintegrity constraint during query processing. For example, in someembodiments, when database management system 102 receives a query,database management system 102 may determine a constraint datastatistics object associated with the query. Database management system102 may then determine whether a dynamic data integrity constraint ofthe constraint data statistics object is consistent with a data state ofdatabase 104. If the constraint data statistics object is consistentwith the data state of database 104, then database management system 102may compare the query against the dynamic data integrity constraint ofthe constraint data statistics object.

FIG. 1 further illustrates performing dynamic partition pruning usingconstraint data statistics objects. However, as would be appreciated bya person of ordinary skill in the art, database system 100 may also useconstraint data statistics objects as dynamic data integrity constraintsto perform query optimization, semi-join reduction optimization, querytransformation, or other various other types of operations.

In some embodiments, database management system 102 may perform dynamicpartition pruning using constraint data statistics objects in order toreduce memory consumption and query processing time. For example, insome embodiments, database management system 102 may partition databasetable 106 into a partition 108-1 containing recently accessed data, andpartitions 108-2 and 108-3 containing data that has not been recentlyaccessed.

In some embodiments, database management system 102 may partitiondatabase table 106 into partitions 108-1, 108-2, and 108-3 using a rangeof values (e.g., range partitioning). However, as would be appreciatedby a person of ordinary skill in the art, database management system 102may partition database table 106 into partitions 108-1, 108-2, and 108-3using various other partition criterion, e.g., hash partitioning.Moreover, as would be appreciated by a person of ordinary skill in theart, database management system 102 may partition database table 106into various numbers of partitions based on a partition criterion.

In some embodiments, database management system 102 may store partitions108-1 to 108-3 on a same physical database node. In some otherembodiments, database management system 102 may store partitions 108-1to 108-3 across several database nodes.

In some embodiments, database management system 102 may store partition108-1 (e.g., a hot partition) in a fast, low latency storage (e.g.,random access memory (RAM)) because database management system 102expects partition 108-1 to be more frequently accessed than partitions108-2 and 108-3 (e.g., cold partitions). Database management system 102may store partitions 108-2 and 108-3 in a slower, higher latency storagedevice such as hard disk drive.

In some embodiments, in response to a query for a recently accessed datarecord, database management system 102 may scan and process the datarecord in partition 108-1 from the fast, low latency storage and skippartitions 108-2 and 108-3 that are irrelevant to the query. Therefore,database management system 102 performance of dynamic partition pruningusing constraint data statistics objects may improve query processingtime and reduce memory consumption because database management system102 does not need to scan, or load into main memory, partitions 108-2and 108-3.

In some embodiments, database management system 102 may perform dynamicpartition pruning using constraint data statistics objects similarly tostatic partition pruning. In some embodiments, for example, databasemanagement system 102 may compare a predicate of a query on a column ofdatabase table 106 against an implied dynamic data integrity constraintof a constraint data statistics object describing data in the column forone of partition 108-1, 108-2, or 108-3, as well as the state of thedata when the statistics objects where last built. Database managementsystem 102 may prune or skip the partition if the predicate of the queryon the column of database table 106 is disjoint with the implied dynamicdata integrity constraint describing the data in the column of thepartition.

In some embodiments, database management system 102 may perform dynamicpartition pruning on database table 106 using one set of primary columnsof database table 106. In some embodiments, database management system102 may also perform dynamic partition pruning on database table 106after static partition pruning.

FIG. 2 illustrates database table 106 with dynamic partition pruningusing constraint data statistics objects, according to an exampleembodiment. As discussed, database management system 102 may partitiondatabase table 106 into partitions 108-1, 108-2, and 108-3.

In some embodiments, database management system 102 partitions databasetable 106 based on a partition criterion for column 202. For example, insome embodiments, database management system 102 may partition databasetable 106 based on a range of values in column 202. As would beappreciated by a person of ordinary skill in the art, databasemanagement system 102 may partition database table 106 based on variousother partition criterion. Moreover, as would be appreciated by a personof ordinary skill in the art, database management system 102 maypartition various other database objects (e.g., a database index) forvarious other dimensions (e.g., row).

In some embodiments, partitions of partition database table 106 mayreside on a single server in database system 100. In some otherembodiments, different partitions of partition database table 106 mayreside on different servers in database system 100. In some otherembodiments, a partition of partition database table 106 may reside on aserver in database system 100 and another partition of partitiondatabase table 106 may reside on an extended storage system in databasesystem 100.

In some embodiments, database management system 102 may create aconstraint data statistics object 204 to represent a range of values forcolumn 202 of each partition 108. For example, database managementsystem 102 may create constraint data statistics object 204-1 forpartition 108-1, constraint data statistics object 204-2 for partition108-2, and constraint data statistics object 204-3 for partition 108-3.

In some embodiments, database management system 102 may perform dynamicpartition pruning using one or more of constraint data statistics object204-1, constraint data statistics object 204-2, and constraint datastatistics object 204-3. In some embodiments, database management system102 may determine that an implied dynamic data integrity constraint ofone (or more than one) of constraint data statistics object 204-1,constraint data statistics object 204-2, and constraint data statisticsobject 204-3 is consistent with a data state of database 104 prior toperforming a query. For example, database management system 102 maydetermine that the implied dynamic data integrity constraint ofconstraint data statistic 204-1 reflects current data for column 202 inpartition 108-1 for database table 106.

For example, in some embodiments, if database management system 102determines the implied dynamic data integrity constraint of constraintdata statistics object 204-1 reflects current data state for column 202in partition 108-1 for database table 106, database management system102 may prune or skip partition 108-1 if a predicate of the query oncolumn 202 of database table 106 is disjoint with the implied dynamicdata integrity constraint of constraint data statistic 204-1 describingthe data in column 202 of partition 108-1.

In some embodiments, if database management system 102 determines theimplied dynamic data integrity constraint of constraint data statistic204-1 does not reflect current data state (e.g., is inconsistent) forcolumn 202 in partition 108-1 for database table 106, databasemanagement system 102 may update the implied dynamic data integrityconstraint of constraint data statistic 204-1 based on the current datain partition 108-1. In some embodiments, if database management system102 determines there is a data change to partition 108-1, databasemanagement system 102 may update the implied dynamic data integrityconstraint of constraint data statistic 204-1 based on the current datain partition 108-1. In some embodiments, database management system 102may update the implied dynamic data integrity constraint immediately. Insome other embodiments, database management system 102 may schedule theupdate of the implied dynamic data integrity constraint for a later time(e.g., asynchronously).

FIG. 3 is a block diagram of a constraint data statistics object 302,according to an example embodiment. Constraint data statistics object302 may represent one of constraint data statistics object 204-1,constraint data statistics object 204-2, and constraint data statisticsobject 204-3 in FIG. 2 . FIG. 3 is discussed with reference to, andwithout limitation to, FIGS. 1 and 2 . In some embodiments, constraintdata statistics object 302 may include consistency metadata 304 andimplied constraint 306. Implied constraint 306 may represent an implieddata integrity constraint for column 202 of a partition 108 of databasetable 106. In some other embodiments, constraint data statistics object302 may include implied constraint 306 but not consistency metadata 304.

In some embodiments, database management system 102 may determinewhether an implied constraint 306 reflects current data for column 202in a partition 108 for database table 106 at a given database snapshot.In other words, database management system 102 determines whetherimplied constraint 306 is consistent with a data state of column 202 ina partition 108 in database 104 at a given database snapshot. Databasemanagement system 102 may determine the consistency of impliedconstraint 306 to determine whether it can use implied constraint 306during a query execution. This ensures that database management system102 is performing optimizations leveraging the integrity constraint(e.g. dynamic partition pruning) using accurate data.

In some embodiments, database management system 102 may determinewhether implied constraint 306 is consistent by building and maintaininga version of constraint data statistics object 302 per databasesnapshot. In some embodiments, an instantiation of a constraint datastatistics object 302 may be referred to as a synopsis. In someembodiments, a synopsis may have content representing a data statistic,and thus implied constraint 306. In some embodiments, a synopsis mayalso have consistency metadata 304.

In some embodiments, database management system 102 may determinewhether implied constraint 306 is consistent by selecting a version ofconstraint data statistics object 302 associated with the databasesnapshot of a query to be performed. Database management system 102 maythen determine whether a predicate of the query is disjoint with theimplied constraint 306 of the selected constraint data statistics object302.

In some embodiments, however, maintaining a version of constraint datastatistics object 302 (e.g., synopsis) per database snapshot isexpensive. This is because extra storage may be required to store eachversion of constraint data statistics object 302 per database snapshot.Moreover, extra effort may be required to maintain the freshness of eachconstraint data statistics object 302 per operation that may invalidatethe constraint data statistics object 302 in the corresponding snapshot.In addition, database management system 102 may need to performadditional processing to select the appropriate constraint datastatistics object 302 at a given database snapshot that wants to use aconstraint data statistics object for performance improvement.

In some embodiments, database management system 102 may insteaddetermine whether implied constraint 306 is consistent by augmentingconstraint data statistics object 302 with consistency metadata 304. Insome embodiments, database management system 102 may use consistencymetadata 304 to decide if constraint data statistics object 302 isconsistent at a given database snapshot for a query. In someembodiments, the inclusion of consistency metadata 304 in constraintdata statistics object 302 means that a separate version of constraintdata statistics objects 302 does not need to be maintained per databasesnapshot.

In some embodiments, database management system 102 may use consistencymetadata 304 because it adds no extra cost to operations that modifycolumn content (e.g., data of column 202). In addition, databasemanagement system 102 may use consistency metadata 304 because it allowslow verification overhead of implied constraint 306 (e.g., datastatistic consistency) with the current state of a column (e.g., column202) of a partition (e.g., partition 108) of a database table (e.g.,database table 106).

In some embodiments, consistency metadata 304 of constraint datastatistics object 302 may include a MaxRowID value. In some embodiments,the MaxRowID value may be the maximum of the largest row identifier of apartition (e.g., partition 108) of database table 106 at a given time.In some embodiments, database management system 102 may store a MaxRowIDvalue with each partition (e.g., partition 108) for database table 106.In some embodiments, database management system 102 may increment theMaxRowID value of each partition (e.g., partition 108) for databasetable 106 when a row is inserted into (or updated in) the partition.Thus, the MaxRowID value of the partition may represent the physicalstate of the partition with no extra cost because it is an existingpiece of information that database management system 102 manages foreach partition.

In some embodiments, database management system 102 may determinewhether implied constraint 306 is consistent with a data state ofdatabase 104 by comparing the MaxRowID value of consistency metadata 304against the current MaxRowID of partition 108. In some embodiments, ifdatabase management system 102 determines the MaxRowID value ofconsistency metadata 304 is equal to the MaxRowID value of the partition108, database management system 102 may decide that implied constraint306 (e.g., the data statistic of constraint data statistic 302) isconsistent with a data state for a query (e.g., a requesting transactiondatabase state) with the snapshot in which the query is executed.However, if database management system 102 determines the MaxRowID valueof consistency metadata 304 is greater than the MaxRowID value of thepartition 108, database management system 102 may not be able to decideif implied constraint 306 is consistent with the data state for thequery (e.g., the requesting transaction database state).

In some embodiments, database management system 102 may use impliedconstraint 306 to perform query optimization. For example, databasemanagement system 102 may use implied constraint 306 to skip (e.g.,prune) an associated partition 108 during dynamic partition pruning.

For example, in some embodiments, a database administrator may define animplied constraint 306 as a minimum and maximum value pair for a column(e.g., column 202) in the associated partition 108 in database table106. This minimum and maximum value pair may represent the smallest andthe largest values that appear in column 202 in the associated partition108 of database table 106. In some embodiments, database managementsystem 102 may build and manage constraint data statistics object 302.As a result, database management system 102 may ensure that impliedconstraint 306 is dynamically updated when the data in database table106 is changed.

In some embodiments, database management system 102 may skip (e.g.,prune) the associated partition 108 based on a query predicate excludingthe range of the minimum and maximum values of the associated partition108 for column 202 based on the implied constraint 306. In other words,database management system 102 may perform dynamic partition pruning atruntime. This is different than static partition pruning because thepruning is based on the current data in an associated partition, as wellas the data state.

FIG. 4 is a flowchart for a method 400 for using traditional datastatistics objects as dynamic data integrity constraints, according tosome embodiments. Method 400 can be performed by processing logic thatcan comprise hardware (e.g., circuitry, dedicated logic, programmablelogic, microcode, etc.), software (e.g., instructions executing on aprocessing device), or a combination thereof. It is to be appreciatedthat not all steps may be needed to perform the disclosure providedherein. Further, some of the steps may be performed simultaneously, orin a different order than shown in FIG. 4 , as will be understood by aperson of ordinary skill in the art.

In 402, database management system 102 defines a data statistics objectfor a column of a partition or a plurality of partitions of a databasetable. In some embodiments, database management system 102 may definethe data statistics object as a minimum and maximum value pair for thecolumn of the partition of the database table. As would be appreciatedby a person of ordinary skill in the art, database management system 102may define the data statistics object based on various other types ofstatistical functions. In some embodiments, database management system102 may build and manage the data statistics object.

In 404, database management system 102 creates a constraint datastatistics object based on the data statistic. In some embodiments, theconstraint data statistics object may be a special type of datastatistics object.

In 406, database management system 102 receiving a query for thedatabase table. In some embodiments, the query may be a selection query,insertion query, modification query, or deleting query. In someembodiments, the query may be a Structured Query Language (SQL) query.

In 408, database management system 102 determines whether a constraintdata statistics object is consistent with a data state of the column ofthe partition. In some embodiments, database management system 102 maydetermine the constraint data statistics object is consistent with thedata state of the column of the partition using consistency metadata inthe constraint data statistics object. In some embodiments, for example,the consistency metadata may be the associated MaxRowID value.

In 408, database management system 102 derives an implied integrityconstraint based on the constraint data statistics object. For example,database management system 102 may derive the implied integrityconstraint based on the statistical value being tracked in theconstraint data statistics object (e.g., the minimum and maximum valuepair for the column of the partition of the database table).

In 410, database management system 102 processes the query for thepartition based on the implied constraint. For example, databasemanagement system 102 may perform dynamic partition pruning for thequery based on the implied constraint. As would be appreciated by aperson of ordinary skill in the art, database management system 102 mayperform query transformation, runtime optimizations, and semi-joinreduction, or various other types of operations (including queryoptimization steps) for the query based on the implied constraint.

FIG. 5 is a flowchart for a method 500 for a dynamic partition pruningprocess that uses data statistics objects as data integrity constraints,according to some embodiments. As would be appreciated by a person ofordinary skill in the art, method 500 may involve other queryoptimization processes including, but not limited to, querytransformation, runtime optimizations, and semi-join reduction that maybe performed using data statistics objects as data integrityconstraints. Method 500 can be performed by processing logic that cancomprise hardware (e.g., circuitry, dedicated logic, programmable logic,microcode, etc.), software (e.g., instructions executing on a processingdevice), or a combination thereof. It is to be appreciated that not allsteps may be needed to perform the disclosure provided herein. Further,some of the steps may be performed simultaneously, or in a differentorder than shown in FIG. 5 , as will be understood by a person ofordinary skill in the art.

In 502, database management system 102 partitions a database table intoa plurality of partitions based on a partition criterion. In someembodiments, database management system 102 may store the partitions onthe same physical database node. In some other embodiments, databasemanagement system 102 may store the partitions across several databasenodes. In some embodiments, database management system 102 may age thedatabase table by partitioning the database table into a plurality ofphysically independent partitions using range partitioning or variousother partitioning criterion as would be appreciated by a person ofordinary skill in the art. For example, database management system 102may partition an ORDERS database table into hot partition containingorders from the last two years, and one or more cold partitions thateach contain the orders for a single calendar year.

In 504, database management system 102 creates a data statistics objectfor a partition of the database table. In some embodiments, databasemanagement system 102 creates the data statistics object for a column ofthe partition of the database table. In some other embodiments, databasemanagement system 102 may create the data statistics object for a row ofthe partition of the database table. In some embodiments, the datastatistics object is a constraint data statistics object that includesconsistency metadata and an implied constraint. In some embodiments, theconsistency metadata may be a MaxRowID value. The MaxRowID value mayrepresent a state of a partition of the database table. The MaxRowID maystore the maximum row identifier value for the partition when the datastatistics object was created or last updated. The constraint mayrepresent a dynamic data integrity constraint. For example, in someembodiments, the implied integrity constraint may be a minimum andmaximum value pair for a column of a partition of the database table.

In 506, database management system 102 receives a query for the databasetable;

In 508, database management system 102 determines that the datastatistics object is consistent. In some embodiments, databasemanagement system 102 may compare the MaxRowID value in the datastatistic object's consistency metadata to the MaxRowId value of apartition of the database table, when the query is being processed.Database management system 102 may determine that the data statisticsobject is consistent if the MaxRowID value in the data statisticsobject's consistency metadata is equal to the MaxRowId value of thepartition.

In 510, database management system 102 performs dynamic partitionpruning in response to the query using the data statistics object. Insome embodiments, database management system 102 may skip loading andscanning a partition of the database table during query processing ifvalues satisfying a predicate for the query does not satisfy the datastatistics object's implied constraint. For example, in someembodiments, database management system 102 may compare the valuessatisfying the predicate of the query to the minimum and maximum valuepair of the data statistics object. Database management system 102 mayskip loading and scanning a partition if none of the values satisfyingthe predicate of the query is within the minimum and maximum value rangeof the data statistics object.

In 512, database management system 102 processes the query usingnon-skipped partitions of the database table.

FIG. 6 is a flowchart for a method 600 for performing consistencychecking of constraint data statistics objects, according to someembodiments. Method 600 can be performed by processing logic that cancomprise hardware (e.g., circuitry, dedicated logic, programmable logic,microcode, etc.), software (e.g., instructions executing on a processingdevice), or a combination thereof. It is to be appreciated that not allsteps may be needed to perform the disclosure provided herein. Further,some of the steps may be performed simultaneously, or in a differentorder than shown in FIG. 6 , as will be understood by a person ofordinary skill in the art.

In 602, database management system 102 receives a query for a databasetable. In some embodiments, the query may a selection query, insertionquery, modification query, or deleting query. In some embodiments, thequery may be a Structured Query Language (SQL) query.

In 604, database management system 102 determines a constraint datastatistics object associated with a column of a partition of thedatabase table.

In 606, database management system 102 determines consistency metadataof the constraint data statistics object is consistent with a data stateof the column of the partition of the database table.

In 608, database management system 102 processes the query for thedatabase table based on determining the consistency metadata of theconstraint data statistics object is consistent with the data state ofthe column of the partition of the database table. In some embodiments,database management system 102 may determine the constraint datastatistics object is consistent with the data state of the column of thepartition using the MaxRowID value of the consistency metadata in theconstraint data statistics object.

Various embodiments can be implemented, for example, using one or morecomputer systems, such as computer system 700 shown in FIG. 7 . Computersystem 700 can be used, for example, to implement method 400 of FIG. 4 .Computer system 700 can be any computer capable of performing thefunctions described herein.

Computer system 700 can be any well-known computer capable of performingthe functions described herein.

Computer system 700 includes one or more processors (also called centralprocessing units, or CPUs), such as a processor 704. Processor 704 isconnected to a communication infrastructure or bus 706.

One or more processors 704 may each be a graphics processing unit (GPU).In an embodiment, a GPU is a processor that is a specialized electroniccircuit designed to process mathematically intensive applications. TheGPU may have a parallel structure that is efficient for parallelprocessing of large blocks of data, such as mathematically intensivedata common to computer graphics applications, images, videos, etc.

Computer system 700 also includes user input/output device(s) 703, suchas monitors, keyboards, pointing devices, etc., that communicate withcommunication infrastructure 706 through user input/output interface(s)702.

Computer system 700 also includes a main or primary memory 708, such asrandom access memory (RAM). Main memory 708 may include one or morelevels of cache. Main memory 708 has stored therein control logic (i.e.,computer software) and/or data.

Computer system 700 may also include one or more secondary storagedevices or memory 710. Secondary memory 710 may include, for example, ahard disk drive 712 and/or a removable storage device or drive 714.Removable storage drive 714 may be a floppy disk drive, a magnetic tapedrive, a compact disk drive, an optical storage device, tape backupdevice, and/or any other storage device/drive.

Removable storage drive 714 may interact with a removable storage unit718. Removable storage unit 718 includes a computer usable or readablestorage device having stored thereon computer software (control logic)and/or data. Removable storage unit 718 may be a floppy disk, magnetictape, compact disk, DVD, optical storage disk, and/any other computerdata storage device. Removable storage drive 714 reads from and/orwrites to removable storage unit 718 in a well-known manner.

According to an exemplary embodiment, secondary memory 710 may includeother means, instrumentalities or other approaches for allowing computerprograms and/or other instructions and/or data to be accessed bycomputer system 700. Such means, instrumentalities or other approachesmay include, for example, a removable storage unit 722 and an interface720. Examples of the removable storage unit 722 and the interface 720may include a program cartridge and cartridge interface (such as thatfound in video game devices), a removable memory chip (such as an EPROMor PROM) and associated socket, a memory stick and USB port, a memorycard and associated memory card slot, and/or any other removable storageunit and associated interface.

Computer system 700 may further include a communication or networkinterface 724. Communication interface 724 enables computer system 700to communicate and interact with any combination of remote devices,remote networks, remote entities, etc. (individually and collectivelyreferenced by reference number 728). For example, communicationinterface 724 may allow computer system 700 to communicate with remotedevices 728 over communications path 726, which may be wired and/orwireless, and which may include any combination of LANs, WANs, theInternet, etc. Control logic and/or data may be transmitted to and fromcomputer system 700 via communication path 726.

In an embodiment, a tangible, non-transitory apparatus or article ofmanufacture comprising a tangible, non-transitory computer useable orreadable medium having control logic (software) stored thereon is alsoreferred to herein as a computer program product or program storagedevice. This includes, but is not limited to, computer system 700, mainmemory 708, secondary memory 710, and removable storage units 718 and722, as well as tangible articles of manufacture embodying anycombination of the foregoing. Such control logic, when executed by oneor more data processing devices (such as computer system 700), causessuch data processing devices to operate as described herein.

Based on the teachings contained in this disclosure, it will be apparentto persons skilled in the relevant art(s) how to make and useembodiments of this disclosure using data processing devices, computersystems and/or computer architectures other than that shown in FIG. 7 .In particular, embodiments can operate with software, hardware, and/oroperating system implementations other than those described herein.

It is to be appreciated that the Detailed Description section, and notany other section, is intended to be used to interpret the claims. Othersections can set forth one or more but not all exemplary embodiments ascontemplated by the inventor(s), and thus, are not intended to limitthis disclosure or the appended claims in any way.

While this disclosure describes exemplary embodiments for exemplaryfields and applications, it should be understood that the disclosure isnot limited thereto. Other embodiments and modifications thereto arepossible, and are within the scope and spirit of this disclosure. Forexample, and without limiting the generality of this paragraph,embodiments are not limited to the software, hardware, firmware, and/orentities illustrated in the figures and/or described herein. Further,embodiments (whether or not explicitly described herein) havesignificant utility to fields and applications beyond the examplesdescribed herein.

Embodiments have been described herein with the aid of functionalbuilding blocks illustrating the implementation of specified functionsand relationships thereof. The boundaries of these functional buildingblocks have been arbitrarily defined herein for the convenience of thedescription. Alternate boundaries can be defined as long as thespecified functions and relationships (or equivalents thereof) areappropriately performed. Also, alternative embodiments can performfunctional blocks, steps, operations, methods, etc. using orderingsdifferent than those described herein.

References herein to “one embodiment,” “an embodiment,” “an exampleembodiment,” or similar phrases, indicate that the embodiment describedcan include a particular feature, structure, or characteristic, butevery embodiment can not necessarily include the particular feature,structure, or characteristic. Moreover, such phrases are not necessarilyreferring to the same embodiment. Further, when a particular feature,structure, or characteristic is described in connection with anembodiment, it would be within the knowledge of persons skilled in therelevant art(s) to incorporate such feature, structure, orcharacteristic into other embodiments whether or not explicitlymentioned or described herein. Additionally, some embodiments can bedescribed using the expression “coupled” and “connected” along withtheir derivatives. These terms are not necessarily intended as synonymsfor each other. For example, some embodiments can be described using theterms “connected” and/or “coupled” to indicate that two or more elementsare in direct physical or electrical contact with each other. The term“coupled,” however, can also mean that two or more elements are not indirect contact with each other, but yet still co-operate or interactwith each other.

The breadth and scope of this disclosure should not be limited by any ofthe above-described exemplary embodiments, but should be defined only inaccordance with the following claims and their equivalents.

What is claimed is:
 1. A computer-implemented method for using datastatistics as dynamic data integrity constraints, comprising: creating,by at least one processor of a database management system (DBMS), aconstraint data statistics object, wherein the constraint datastatistics object stores and tracks a single data statistic of a singledatabase object, the constraint data statistics object storesconsistency metadata that specifies a most recent time point when thesingle database object was created or last updated, and the DBMS isconfigured to automatically update the constraint data statistics objectin response to a data change being made to the single database object;receiving, by the at least one processor, a query referencing the singledatabase object; in response to receiving the query, determining, by theat least one processor, the single data statistic stored in theconstraint data statistics object reflects a current data state of thesingle database object using the consistency metadata; deriving, by theat least one processor, a dynamic data integrity constraint for thesingle database object from the single data statistic stored in theconstraint data statistics object in response to the determining,wherein the dynamic data integrity constraint defines a condition forinclusion of data in the single database object; and executing, by theat least one processor, the query for the single database objectaccording to the dynamic data integrity constraint for the singledatabase object, thereby producing a result, wherein the executingcomprises comparing a predicate of the query against the condition ofthe dynamic data integrity constraint for the single database object. 2.The computer-implemented method of claim 1, further comprising: updatingthe single data statistic stored in the constraint data statisticsobject based on the current data state of the single database object. 3.The computer-implemented method of claim 1, the determining furthercomprising: comparing the consistency metadata to the current data stateof the single database object.
 4. The computer-implemented method ofclaim 1, the determining further comprising: determining a databasesnapshot associated with the query.
 5. The computer-implemented methodof claim 1, the creating further comprising: defining the single datastatistic stored in the constraint data statistics object for a columnor a set of columns of the single database object.
 6. Thecomputer-implemented method of claim 1, the executing furthercomprising: performing at least one of dynamic partition pruning, queryoptimization, semi-join reduction optimization, or query transformation.7. The computer-implemented method of claim 1, the executing furthercomprising: skipping a portion of the single database object based onthe predicate of the query being disjoint with the condition of thedynamic data integrity constraint for the single database object.
 8. Asystem, comprising: a memory; and at least one processor coupled to thememory and configured to: create a constraint data statistics object,wherein the constraint data statistics object stores and tracks a singledata statistic of a single database object, the constraint datastatistics object stores consistency metadata that specifies a mostrecent time point when the single database object was created or lastupdated, and the at least one processor is configured to automaticallyupdate the constraint data statistics object in response to a datachange being made to the single database object; receive a queryreferencing the single database object; in response to receiving thequery, determine the single data statistic stored in the constraint datastatistics object reflects a current data state of the single databaseobject using the consistency metadata; derive a dynamic data integrityconstraint for the single database object from the single data statisticstored in the constraint data statistics object in response to thedetermining, wherein the dynamic data integrity constraint defines acondition for inclusion of data in the single database object; andexecute the query for the single database object according to thedynamic data integrity constraint for the single database object,thereby producing a result, wherein the executing comprises comparing apredicate of the query against the condition of the dynamic dataintegrity constraint for the single database object.
 9. The system ofclaim 8, wherein the at least one processor is further configured to:update the single data statistic stored in the constraint datastatistics object based on the current data state of the single databaseobject.
 10. The system of claim 8, wherein to determine the single datastatistic stored in the constraint data statistics object reflects thecurrent data state of the single database object, the at least oneprocessor is further configured to: compare the consistency metadata tothe current data state of the single database object.
 11. The system ofclaim 8, wherein to determine the single data statistic stored in theconstraint data statistics object reflects the current data state of thesingle database object, the at least one processor is further configuredto: determine a database snapshot associated with the query.
 12. Thesystem of claim 8, wherein to create the constraint data statisticsobject, the at least one processor is further configured to: define thesingle data statistic stored in the constraint data statistics objectfor a column or a set of columns of the single database object.
 13. Thesystem of claim 8, wherein to execute the query, the at least oneprocessor further is configured to: perform at least one of dynamicpartition pruning, query optimization, semi-join reduction optimization,or query transformation.
 14. The system of claim 8, wherein to executethe query, the at least one processor further configured to: skip aportion of the single database object based on the predicate of thequery being disjoint with the condition of the dynamic data integrityconstraint for the single database object.
 15. A non-transitorycomputer-readable medium having instructions stored thereon that, whenexecuted by at least one computing device, cause the at least onecomputing device to perform operations comprising: creating a constraintdata statistics object, wherein the constraint data statistics objectstores and tracks a single data statistic of a single database object,the constraint data statistics object stores consistency metadata thatspecifies a most recent time point when the single database object wascreated or last updated, and the at least one computing device isconfigured to automatically update the constraint data statistics objectin response to a data change being made to the single database object;receiving a query referencing the single database object; in response toreceiving the query, determining the single data statistic stored in theconstraint data statistics object reflects a current data state of thesingle database object using the consistency metadata; deriving adynamic data integrity constraint for the single database object fromthe single data statistic stored in the constraint data statisticsobject in response to the determining, wherein the dynamic dataintegrity constraint defines a condition for inclusion of data in thesingle database object; and executing the query for the single databaseobject according to the dynamic data integrity constraint for the singledatabase object, thereby producing a result, wherein the executingcomprises comparing a predicate of the query against the condition ofthe dynamic data integrity constraint for the single database object.16. The non-transitory computer-readable medium of claim 15, theoperations further comprising: updating the single data statistic storedin the constraint data statistics object based on the current data stateof the single database object.
 17. The non-transitory computer-readablemedium of claim 15, the determining further comprising: comparing theconsistency metadata to the current data state of the single databaseobject.
 18. The non-transitory computer-readable medium of claim 15, thedetermining further comprising: determining a database snapshotassociated with the query.
 19. The non-transitory computer-readablemedium of claim 15, the creating further comprising: defining the singledata statistic stored in the constraint data statistics object for acolumn or a set of columns of the single database object.
 20. Thenon-transitory computer-readable medium of claim 15, the executingfurther comprising: performing at least one of dynamic partitionpruning, query optimization, semi-join reduction optimization, or querytransformation.